why: The socket_path/env plumbing that opens each from_env example is
needed for the doctest to execute but is noise to the reader. Marking it
hidden runs it as a test while keeping it out of the rendered docs.

what:
- Tag the setup lines in Server/Window/Pane.from_env with
  `# doctest: +HIDE`; split the env dicts so the marker fits <=88 cols.
- Session.from_env hides only socket_path — its env carries the
  deliberately wrong session id the surrounding prose explains, so it
  stays visible (hide plumbing, not meaning).
- TEMP: pin gp-libs / gp-sphinx to the branches carrying the HIDE
  optionflag and the render strip (git-pull/gp-libs#79,
  git-pull/gp-sphinx#65) via [tool.uv.sources]; revert to releases once
  they land.

why: The socket_path/env plumbing that opens each from_env example is
needed for the doctest to execute but is noise to the reader. Marking it
hidden runs it as a test while keeping it out of the rendered docs.

what:
- Tag the setup lines in Server/Window/Pane.from_env with
  `# doctest: +HIDE`; split the env dicts so the marker fits <=88 cols.
- Session.from_env hides only socket_path — its env carries the
  deliberately wrong session id the surrounding prose explains, so it
  stays visible (hide plumbing, not meaning).
- TEMP: git-branch-pin the three changed packages (gp-libs,
  sphinx-autodoc-api-style, sphinx-autodoc-typehints-gp) to
  doctest-hide-badges; add typehints-gp as a direct dep so uv honors its
  source pin (uv.sources applies to direct deps only). gp-sphinx and its
  JS-asset packages stay on PyPI wheels, so CI needn't build the
  vite/pnpm toolchain. Revert to releases once git-pull/gp-libs#79 and
  git-pull/gp-sphinx#65 publish.

why: The +HIDE marker shipped in #79 with only a CHANGES entry; the
docs site had no how-to explaining when or why to reach for it.

what:
- Add a "Hide a setup line from rendered docs" section to the pytest
  plugin how-to, with a runnable example the docs suite executes
- Note the marker parses under the pytest plugin (.rst, .md, .py) but
  not the standalone doctest_docutils CLI

…ier (#65)

Two independent API-documentation polish changes. One hides incidental
doctest setup from rendered autodoc output while the example still runs
as a test; the other stops class-member modifiers from rendering twice.

- **Hide `+HIDE` doctest setup** (`typehints-gp`): doctest lines tagged
  `# doctest: +HIDE` are dropped from the rendered docstring, along with
  their `...` continuations, so plumbing like an `env` mapping or a
  socket path executes without cluttering the example. The strip runs
  at Sphinx build time; the source docstring — and the test that runs
  from it — is untouched.
- **Fix double-rendered modifiers** (`api-style`): members marked
  `classmethod`, `staticmethod`, `async`, or `abstract` showed the
  modifier twice — once as a signature prefix, once as the badge beside
  it. The redundant prefix is dropped so each modifier appears only in
  its badge; `property`/`type` word prefixes are left untouched.
- **Documentation**: the `typehints-gp` how-to gains a "Hiding
  incidental doctest setup" section covering the flag and the
  doctest-runner registration it needs.

See also: git-pull/gp-libs#79